<H1>Appendix E</B>: <A NAME=MARKER-9-1> </A> RISC OS file types</H1>
<HR>
File typ<A NAME=MARKER-2-2> </A> es are three-digit hexadecimal numbers. They are divided into ranges</B>:
<UL>
<LI><B>E00 - FFF</B>: allocated by Acorn for generic data types
<LI><B>B00 - DFF</B>: allocated by Acorn to software houses for applications
<LI><B>A00 - AFF</B>: reserved for use by Acorn applications
<LI><B>400 - 9FF</B>: allocated by Acorn to software houses for applications
<LI><B>100 - 3FF</B>: allocated by Acorn to individuals for applications
<LI><B>000 - 0FF</B>: free for users</UL>
<P>
For each type, there may be a default action on loading and running the file. These actions may change, depending on whether the desktop is in use, and which applications have been seen. The system variables <A NAME=MARKER-2-3> </A> Alias$@LoadType_XXX and <A NAME=MARKER-2-4> </A> Alias$@RunType_XXX give the actions (XXX = file type). <P>
Some types have a textual equivalent set at start-up, which may be used in most commands (but not in the above system variables) instead of the hexadecimal code. These are indicated in the table below by a 'T'. For example, file type &FFF is set at start-up to have the textual equivalent <CODE>Text</CODE> . Other textual equivalents may be set as an application starts - for example, Acorn Desktop Publisher sets up file type &AF9 to be <CODE>DtpDoc</CODE> , and file type &AFA to be <CODE>DtpStyle</CODE> . These textual equivalents are set using the system variables <A NAME=MARKER-2-5> </A> File$Type_XXX, where XXX is the file type.<P>
You should use the hexadecimal file type in command scripts and in programs, otherwise you will find that your files will give an error if you try to run them on a machine that uses a territory with different textual equivalents.<P>
The following types are currently used or reserved by Acorn. Not all file types used by software houses are shown. This list may be extended from time to time</B>:<P>
